Important: Make sure at least one packet processing card is active before you configure system elements. Refer to Configuring System Settings in this guide for information and instructions on activating packet processing cards.
Important: Commands used in the configuration examples in this section represent the most common or likely commands and/or keyword options. In many cases, other commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all commands.
Important: We recommend that if your system is using Fast Ether Line Cards (FELCs, Ethernet 10/100), at least one context be configured per physical port in order to ensure adequate bandwidth for subscriber sessions.The output is a two-column table similar to the example below. This example shows that two contexts were created: one named source and one named destination.
|
Step 2
|
Save your configuration as described in the Verifying and Saving Your Configuration chapter.
|
|
Step 1
|
|
Step 2
|
|
Step 3
|
Important: This section provides the minimum instructions for configuring interfaces and ports to allow the system to communicate on the network. Commands that configure additional interface or port properties are provided in the Ethernet Port Configuration Mode and Ethernet Interface Configuration Mode chapters of the Command Line Interface Reference.
Caution: To ensure that system line card and port-level redundancy mechanisms function properly, the Spanning Tree protocol must be disabled on devices connected directly to any system port. Failure to turn off the Spanning Tree protocol may result in failures in the redundancy mechanisms or service outage.|
•
|
Optional: Add the loopback keyword option to the interface <name> command, to set the interface type as “loopback” which is always UP and not bound to any physical port.
|
|
•
|
Optional: Add the secondary keyword to the { ip | ipv6 } address command, to assign multiple IP addresses to the interface. IP addresses can be entered using IPv4 dotted-decimal or IPv6 colon-separated notation.
|
|
•
|
Optional: In the interface config mode, add the port-switch-on-L3-fail address command, to configure the interface for switchover to the port on the redundant line card if connectivity to a specified IP address is lost. This IP address can be entered using IPv4 dotted-decimal or IPv6 colon-separated notation.
|
|
•
|
For port ethernet slot#, use the actual chassis slot in which the line card is installed. This could be any number from 17 to 23, or 26 to 39, or 42 to 48.
|
|
•
|
For port ethernet port#, on FELCs, this value can be from 1 to 8. For the GELC/GLC2s and XGLCs this value must be 1. For for QGLCs enter a value from 1 to 4.
|
|
•
|
Optional: In the Ethernet Port configuration mode, add the preferred slot slot# command if line card port redundancy was enabled at the card level and you want to specify a port preference.
|
|
•
|
Optional: In the Ethernet Port configuration mode, configure the port speed, if needed, by entering the medium command. Refer to the Command Line Interface Reference for a complete explanation of this command.
|
|
•
|
ip_address and netmask are the IP address and subnet mask of the target network. This IP address can be entered using IPv4 dotted-decimal or IPv6 colon-separated notation.
|
|
•
|
gw_address is the IP address of the default gateway or next-hop route. This IP address can be entered using IPv4 dotted-decimal or IPv6 colon-separated notation.
|
|
Step 1
|
context <context_name>
context_name represents the name of the context in which the interface was created. The output from these commands should be similar to the following example.
In this example an interface named mgmt1 was configured in the local context.
show configuration port <slot#/port#>
slot# is the chassis slot number of the line card on which the physical port resides. slot# can be any integer value from 17 to 39, and 42 to 48.
slot# is the chassis slot number of the MIO on which the physical port resides. slot# can be 5 or 6.
In this example, the port is bound to an interface called rp1 configured in a context called source.
|
Step 4
|
Save the configuration as described in the Verifying and Saving Your Configuration chapter.
|
|
Step 1
|
|
Step 2
|
|
Step 3
|
|
Step 4
|
Important: Do not attempt to bind the link at this time. Complete the rest of the procedure (steps 5, 6, and 7) and return to bind the link to the port. The SS7 link can only be bound to the ATM port after the configuration for the SS7 routing domain has been completed as described in the 3G SGSN Configuration section of the SGSN Administration Guide.|
Step 5
|
Configure the appropriate timing source (BITS from the SPIO or line-timing from an attached remote) to ensure transmit synchronization by applying the example configuration in the Configuring Transmit Timing Source section of the Configuring System Settings chapter.
|
|
Step 6
|
|
Step 7
|
Save the configuration as described in the Verifying and Saving Your Configuration chapter.
|
|
•
|
Entering no shutdown makes the card active.
|
|
•
|
You must enter the point-to-point keyword to create the PVC (Permanent Virtual Connection) interface for the IP over ATM.
|
|
•
|
|
•
|
Complete optional ATM port configuration (see the ATM Port Configuration Mode in the Command Line Interface Reference) and the other steps in this procedure to set timing and save the configuration.
|
Use the following example to bind an already configured SS7 link to a PVC interface for an ATM port:
|
•
|
Save the configuration as described in the Saving Your Configuration chapter.
|
|
Step 1
|
context <context_name>
context_name represents the name of the context in which the interface was created. The output from these commands should look similar to that displayed in the following example.
This command produces an output similar to that displayed in the following example:
|
Step 1
|
|
Step 2
|
|
Step 3
|
Configure the appropriate timing source (BITS from the SPIO or line-timing from attached remote) to ensure transmit synchronization by applying the example configuration in the Configuring Transmit Timing Source section in the Configuring System Settings chapter.
|
Important: Before you can move to Step 4 to bind a DLCI to a port, you must complete the link configuration by configuring Peer-NSEIs and/or SS7 routing domains as described in the SGSN Service Configuration Procedures chapter of the SGSN Administration Guide. Return to this procedure when your link configuration is complete.|
Step 4
|
|
Step 6
|
Save the configuration as described in the Verifying and Saving Your Configuration chapter.
|
|
•
|
Make a note of the information you configure - you will need it again later for the path command used to configure channel characteristics.
|
|
•
|
The default framing_type is SONET for the channelized line card.
|
|
•
|
With releases 8.1 and higher, we recommend that you include the signal type, either ds1 (24 timeslots, 1.536 Mbps) or e1 (32 timeslots, 2.048 Mbps), when defining the framing.
|
|
•
|
With releases 8.1 and higher, you need to set the service-type for the CLC card to frame-relay. All other options are not fully supported at this time.
|
path <path_id> { ds1 | e1 } <number_of_connections> <frame_mapping> <multiplex#> <multiplex#> framing <framing_mode> mapping-mode <mapping_mode> [ timeslots <timeslot#> [ <timeslot#> ] ]
Important: You should record the path definition values you enter as the information will be needed again with other configuration commands. frame-relay path <path_id> { ds1 | e1 } <number_of_connections> [ timeslot <timeslot#> [ intf-type <intf_type> [ lmi-type <lmi_type> ] ] ]
Important: This procedure should not be attempted until after the configuration is completed for Peer-NSEIs and/or SS7 routing domains as described in the SGSN Administration Guide. bind link { peer-nsei <nse_id> ns-vc-id <nsvc_id> | ss7-routing-domain <ss7rd_id> linkset-id <id> link-id <id>}
[local]<hostname>#show port info 27/1
The following display is only a partial output of the show command to illustrate the channelized port and DLCIs.
